I'm curious why the virtual serial here jsut to rewrite gcode command information. I feel like it would be better served to utilize gcode protocol hooks, which can both adapt commands being sent and received.

https://docs.octoprint.org/en/main/plugins/hooks.html#octoprint-comm-protocol-gcode-phase

@jneilliii
You were absolutely right! This is so much easier!!
Thank you for the hint :)

@coc815, thanks for your contribution, your plugin looks great!

For inclusion in the plugin repository, we usually require that log lines (and comments, if desired) be in English. This allows other non-German users to understand and contribute to your work. Could you please update them?

@jacopotediosi all english now

Thanks @jacopotediosi that was going to be something that I mentioned when performing a full review. The other thing I noticed was that version 0.1.0 was not released on GitHub yet. That's a good thing, as it will allow @coc815 to adjust the code prior to release and official review.

I changed the answer to the question, if any kind of genAI was involved from "Copilot" to "No", because after I switched the code to utilize gcode protocol hooks, the code is truely mine ;)

@jneilliii But I must admit, that I am a bit lost now. you mentioned version 0.1.0. If you meant, that I should switch versioning back to 0.1.0, that is done now. If you meant something different, would you be so kind and explain a bit further? I am really new to all of that.

Thank you all for your patience

@coc815 Automatic updates in OctoPrint plugins are managed by the get_update_information function, which looks for the latest release in your GitHub repository.

Currently, you haven't published your first release yet:

Usually the workflow is: implement features and fix bugs and - only when you're ready to release an update to the public - increment the version number in pyproject.toml and create a GitHub Release. Usually version numbers only go upwards, never backwards.

When you create a release, make sure to create a tag with the corresponding version number, e.g. 0.1.0. This is something you can do on the same page while creating a Release.

What @jneilliii was asking you to do is to publish your first release.

For further information, you can refer to the GitHub documentation about releases.

@jacopotediosi Thank's for pointing me in the right direction. I published my first release

@jneilliii I changed the release title and the description

Thank you all :)